fix: parcel giving 404 on localhost:1234 #354
Merged
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
aah! nice catch. Merging. |
dennyabrain
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the error of
parcelgiving us a 404 error on localhost:1234The front end of the browser extension can be just loaded using the
options.jsxfile in theplugin/srcfolder.The error occurring was when we tried to run just the frontend using the
npm run start:options, which triggers this commandparcel src/options.jsxTo fix it we have to actually run the
options.htmlfile using parcel, in which we pass theoptions.jsxfile.now the frontend runs on
localhost:1234